Which rate limit of REST API is correct

[clp_yamasaki (Shintaro Yamasaki)]

I’m looking into how much REST API rate limiting is.

Then, I found two descriptions for it.

1. API document

   • Our rate limits on our REST API is 900 events/min across an entire organization.

   • https://developer.pagerduty.com/docs/rest-api-v2/rate-limiting/
2. Reply comment from a support on the forum

   • REST API - up to 2,000/min per key

   • https://community.pagerduty.com/forum/t/monitoring-api-rate-limiting/3318/2

Could you tell me which is correct?

[Inactive-Member-27144877]

Hello,

Thanks for reaching out on our Community space! We have a REST and an Events API, each with different limits:

1. Events - 120/min (enforced per-integration-key)
2. REST - 900/min (enforced at the account level)

API requests that exceed the API rate limit will return different HTTP status codes depending on which API you are using. REST v2 API will return a 429 code, and our v1 Events API will return a 403 code.

Hope this helps clarify things, please let me know if not or if you have any further questions.

John

[clp_yamasaki (Shintaro Yamasaki)]

@Inactive-Member-27144877
Thank you for replying. I got it.

[xenda.amici]

PagerDuty’s REST API Rate Limiting Refresh

We are rolling out some updates to PagerDuty’s REST API rate limits, including:

1. A refreshed rate limiting system to more consistently and accurately enforce REST API rate limits
2. New response headers within our REST APIs so that customers can programmatically control the request load sent to PagerDuty
3. Four dimensions used to enforce the rate limit

Learn all about PagerDuty’s REST API rate limits:

• Developer Doc
• Support Article
• ChangeLog